Organizational Chart Exporting with Layout Preview and Customization

ABSTRACT

Techniques are described for exporting organizational charts being presented inside a browser window. The system can present an export canvas that identifies the portion of the organizational chart that is to be exported. In some embodiments, the export canvas can be automatically adjusted to prevent collisions with tiles within the organizational chart. In some examples, the export canvas can be presented on a different layer than the organizational chart, thus allowing the export canvas to move around freely without disrupting the underlying organizational chart.

BACKGROUND

An organizational chart is a diagram that graphically shows the structure of an organization and the relationships and ranks of members (or groups) within the organization. The organizational chart can be useful in helping members within the organization visualize who is in the organization and the relationships between different members. Exemplary relations include manager-employee, director to managing directors, and others. Typically, the organizational chart is presented within a window, such as a browser window.

For small business organizations, the entire organization can be presented within an organizational chart in the browser window with ease. However as organizations grow, it becomes difficult to display all the members simultaneously within the browser window. For example, a director can have multiple managers who directly report to the director. Each manager can also include many employees who directly report to the manager. Seeing the relationship between two employees can become difficult given the number of people being displayed can require scrolling around the browser window. Besides displaying the organization, exporting the organizational chart can also be confusing, particularly when the organizational chart expands over multiple pages. This can be very time consuming and confusing.

SUMMARY

In one embodiment, a computer-implemented method presents, by a processor, an organizational chart within a first layer of a window, the organizational chart including a plurality of nodes that each represent an employee within an organization, wherein each node is represented as a tile within the first layer of the window. The method then presents, by the processor, an export canvas within a second layer of the window that overlays the first layer, wherein the export canvas is configured to identify a portion of the organizational chart for export that lies within the within the boundaries of the export canvas. The second layer can be a transparent layer that overlays the first layer. The method then detects, by the processor, an adjustment to the export canvas. The method then determines, by the processor, that the adjustment causes a boundary of the export canvas to collide with a tile representing a node of the organizational chart. The method then automatically updates, by the processor, the export canvas to prevent the collision.

In one example, the method can further present, by the processor, an export menu within the window, the export menu being configured to provide a plurality of options for exporting the organizational chart and automatically update, by the processor, an option from the plurality of options that is associated with the dimension when the dimension is updated to prevent the collision.

In another example, automatically updating the export canvas chart can include determining, by the processor, that a majority of the tile is outside the export canvas and adjusting, by the processor, a dimension of the export canvas such that the tile is within the boundary of the export canvas. Adjusting can include increasing or reducing the dimension. In other examples, the export canvas can be shifted rather than resized.

In another example, automatically updating the export canvas chart can include determining, by the processor, that a majority of the tile is within the export canvas and adjusting, by the processor, a dimension of the export canvas such that the tile is within the boundary of the export canvas. Adjusting can include increasing or reducing the dimension. In other examples, the export canvas can be shifted rather than resized.

In another embodiment, a non-transitory computer readable storage medium stores one or more programs comprising instructions for presenting an organizational chart within a first layer of a window, the organizational chart including a plurality of nodes that each represent an employee within an organization, wherein each node is represented as a tile within the first layer of the window, presenting an export canvas within a second layer of the window that overlays the first layer, wherein the export canvas is configured to identify a portion of the organizational chart for export that lies within the within the boundaries of the export canvas, detecting an adjustment to the export canvas, determining that the adjustment causes a boundary of the export canvas to collide with a tile representing a node of the organizational chart, and automatically updating the export canvas to prevent the collision.

In another embodiment, a computer implemented system comprises one or more computer processors and a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium comprises instructions, that when executed, control the one or more computer processors to be configured for presenting an organizational chart within a first layer of a window, the organizational chart including a plurality of nodes that each represent an employee within an organization, wherein each node is represented as a tile within the first layer of the window, presenting an export canvas within a second layer of the window that overlays the first layer, wherein the export canvas is configured to identify a portion of the organizational chart for export that lies within the within the boundaries of the export canvas, detecting an adjustment to the export canvas, determining that the adjustment causes a boundary of the export canvas to collide with a tile representing a node of the organizational chart, and automatically updating the export canvas to prevent the collision.

The following detailed description and accompanying drawings provide a better understanding of the nature and advantages of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a workflow for presenting a first selected node in an organizational chart according to one embodiment;

FIG. 2 illustrates a workflow for presenting a second selected node in an organizational chart according to one embodiment;

FIG. 3 illustrates another workflow for presenting a selected node in an organizational chart according to one embodiment;

FIG. 4 another illustrates a workflow for presenting a second selected node in an organizational chart according to one embodiment;

FIG. 5 illustrates another workflow for presenting a selected node in an organizational chart according to one embodiment;

FIG. 6 illustrates a workflow for altering an organizational chart in response to a window resize according to one embodiment;

FIGS. 7a, 7b, and 7c illustrate exemplary tile templates according to one embodiment;

FIGS. 8a, 8b, and 8c illustrate exemplary tile templates according to one embodiment;

FIG. 9 illustrates a browser window containing an export menu according to one embodiment;

FIG. 10 illustrates an export menu according to one embodiment;

FIG. 11 illustrates a browser window according to one embodiment;

FIG. 12 illustrates a browser window according to another embodiment;

FIG. 13a illustrates a first export page according to one embodiment;

FIG. 13b illustrates a second export page according to one embodiment;

FIG. 14 illustrates a process for updating an export canvas according to one embodiment; and

FIG. 15 illustrates an exemplary computer system according to one embodiment.

DETAILED DESCRIPTION

In the following description, for purposes of explanation, numerous examples and specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be evident, however, to one skilled in the art that the present disclosure as expressed in the claims may include some or all of the features in these examples alone or in combination with other features described below, and may further include modifications and equivalents of the features and concepts described herein.

Described herein are techniques for dynamically updating the layout of an organizational chart to better utilize the viewable area within window. The window can be a browser window. An organization is typically organized hierarchically, where the highest ranking people are at the apex and the lowest ranking people are at the bottom, thus appearing like a pyramid. The base of the pyramid are members of the organization that do not have any subordinates. In some embodiments, one level of the hierarchy is initially displayed in the browser window. For example, a person of interest can be presented on the apex and the direct reports of the person of interest are presented in a horizontal row below the person of interest. Employees presented in the same row typically appear in the same level of the hierarchical organization. Selecting a direct report can cause the system to present the direct reports of the selected direct report in the organizational chart.

In one embodiment, the system can dynamically alter the layout in which the direct reports are presented according to the number of direct reports that need to be presented. For example, a vertical vector can be used to present the direct reports when the number of direct reports is under a predefined threshold. This can reduce horizontal scrolling to view all the direct reports, thereby improving the visibility of the organizational chart. Alternatively, a two-dimensional matrix can be used to present the direct reports when the number of direct reports is equal to or over the predefined threshold. Viewing a large numbers of direct reports may be easier in a two-dimensional matrix rather than a one-dimensional matrix (e.g., vertical vector) since it reduces vertical scrolling. In other embodiments, the system can dynamically alter the layout based on the number of direct reports to present and the available space in the browser window. For example, the dimensions of the matrix can be selected to maximize the number of direct reports that can be simultaneously presented in the viewable area of the browser window along with the person of interest that is managing the direct reports. In yet other embodiments, selecting multiple nodes in the organizational chart or resizing the browser window can result in the layout of the organizational chart to be dynamically altered.

The system can be implemented on the client side or server side. For example, the system can be implemented on the client device and be configured to update the organizational chart according to user input received on the client device. As another example, the system can be implemented on a server that is in communication with a client device. User input received on the client device can be transmitted from the client device to the server. The server can process the detected user input and update the organizational chart. Once updated, the server can transmit the updated organizational chart or the necessary changes to update the existing organizational to the client device. The client device can present the content received to the user.

FIG. 1 illustrates a workflow for presenting a first selected node in an organizational chart according to one embodiment. Organizational chart 100 is being presented in a window of a graphical user interface. Organizational chart 100 can be generated based on an underlying hierarchical organization. The hierarchical organization is a structure that describes people (or other entities) within the organization as a subordinate or manager. Each person can be represented as a node within the hierarchical organization. Nodes can connect with one another to represent relationships between people. For example, a node representing a manager can be directly connected to a subnode representing a direct report. The placement of the subnode representing the direct report can appear below the node representing the manager. Organizational chart 100 is a visual representation of a view of the hierarchical organization. The view can present a portion of the hierarchical organization with respect to a person of interest. One or more nodes of the hierarchical organization can be presented in the organizational chart. As shown, this view is based on the relationships with a manager in the hierarchical organization that is being represented by node 105. For this reason, node 105 appears at the apex of organizational chart 100. Under node 105, organizational chart 100 includes nodes 112, 114, 116, and 118. These nodes represent the direct reports of the manager. Since nodes 112, 114, 116, and 118 have the same ranking with respect to the manager being represented by node 105, these nodes are appear along the same horizontal plane below node 105. In some embodiments, a node can be visually presented in organizational chart 100 as a tile. The tile can include attributes corresponding to the person that is being represented by the node. For example, the tile can include the person's profile image, name, role/title in the organization, number of direct reports, number of total reports, and other attributes that are related to the person.

The workflow begins at step (1) (reference numeral 151) with the system (which can be a computer system that includes a processor and non-transitory memory) detecting user input on the graphical user interface that is representative of selecting node 114. Node 114 represents an employee and selection of node 114 can be interpreted as an interest to display the direct reports of the employee. Once node 114 has been selected, the workflow continues by identifying the subnodes (e.g., direct reports) of node 114 at step (2) (reference numeral 152). This can be completed by querying the hierarchical organization for the direct reports of node 114. This can be the subnodes that are directly connected to node 114. Once the subnodes have been identified, the workflow can continue by determining a layout to apply to the subnodes at step (3) (reference numeral 153). The layout can be selected from one or more predefined layouts that are applicable to the subnodes. The applicability of a predefined layout to the subnodes can be determined by the number of subnodes that exist. For example, there may be three applicable layouts (4×1, 2×2, and 1×4) that are applicable when there are four subnodes available. Here, the workflow can determine that the layout to apply to the subnodes is a vertical vector since the number of subnodes is below a predefined threshold. Once the layout has been determined, the workflow can continue by presenting the subnodes in a matrix according to the layout at step (4) (reference numeral 154). Here, the layout for matrix 120 is a vertical vector and as a result, subnodes 121-126 are presented in matrix 120 as a vertical vector. Matrix 120 can disappear from organizational chart 100 when user input representative of selecting node 114 a second time is detected. Selecting a node a first time can cause the subnodes of the selected node to appear in organizational chart 100 while selecting the node a second time can cause the subnodes of the selected node to disappear from organizational chart 100.

In some embodiments, more than one node (or subnode) can be selected in the organizational chart. The ability to select multiple nodes (or subnodes) in the organizational chart provides freedom to a user when exploring the hierarchical organization. For example, the direct reports of a first manager can be viewed simultaneously with the direct reports of a second manager. This allows the subordinates of different managers to be compared with one another. As another example, the direct reports of an upper level manager can be viewed simultaneously with the direct reports of a lower level manager where the lower level manager reports to the upper level manager. As a result, multiple levels of hierarchy can be explored at the same time.

FIG. 2 illustrates a workflow for presenting a second selected node in an organizational chart according to one embodiment. Organizational chart 200 can be presented in response to the selection of subnode 122 in organizational chart 100 of FIG. 1. The workflow can begin by detecting user input representative of selecting subnode 122 at step (1) (reference numeral 251). When the selection of subnode 122 is detected, workflow 200 can continue by identifying the sub-subnodes of subnode 122 at step (2) (reference numeral 252). The sub-subnodes represent the direct reports of the employee represented by subnode 122. Identifying the sub-subnodes can include querying the hierarchical organization for the direct reports of subnode 122. Once the sub-subnodes have been identified, the workflow can continue by determining a layout for the sub-subnodes at step (3) (reference numeral 253). In one embodiment, the layout of the sub-subnodes can be determined based on the number of sub-subnodes that exist for subnode 122. For example if the number of sub-subnodes is below a predefined threshold (e.g., 15), then the layout can be a vertical vector. Alternatively if the number of sub-subnodes is above or equal to the predefined threshold, then the layout can be a multi-dimensional matrix. Here, the layout would be a vertical vector since there are three sub-subnodes, which is under the predefined threshold of 15.

Once the layout has been determined, the workflow can proceed by moving the selected subnode (subnode 122) from matrix 120 to a new location in organizational chart 200 at step (4) (reference numeral 254). In one embodiment, the new location can be in the same horizontal plane as matrix 120 to signify that subnode 122 and the subnodes within matrix 120 reside in the same hierarchical level within the hierarchical organization. The new location can be to the left or the right of matrix 120. In one example, the workflow can move subnode 122 to the side of matrix 120 that has more room in organizational chart 200. In another example, the workflow can move subnode 122 to the side of matrix 120 that is more centered in organizational chart 200.

Once subnode 122 has been moved to its new location, the workflow continues by presenting sub-subnodes in matrix 220 according to the determined layout at step (5) (reference numeral 255). Here, sub-subnodes 221, 222, and 223 are presented within matrix 220 in a vertical vector format. Once matrix 220 has been presented, the workflow can optionally adjust the spacing between nodes, subnodes, and sub-subnodes to ensure that minimum spacing requirements are satisfied at step (6) (reference numeral 256). Minimum spacing requirements can specify the amount of space that should exist between elements (nodes, subnodes, matrixes, etc.) within organizational chart 200. For example if the spacing between matrix 120 and matrix 220 violated the minimum spacing requirements, matrix 220 can be moved away from matrix 120 until the minimum spacing requirement is satisfied. This movement can also cause connected nodes (subnodes, etc.) of matrix 220 to also move. For example subnode 122 can also move in the same direction by the same distance as matrix 220 to satisfy the minimum spacing requirement. In some examples, the movement of one element can cause a chain reaction of violations of other spacing requirements. Thus, the workflow can recursively adjust the spacing between elements of organizational chart 200 until all minimum spacing requirements are satisfied.

FIG. 3 illustrates another workflow for presenting a selected node in an organizational chart according to one embodiment. Similar to organizational chart 100 of FIG. 1, organizational chart 300 includes node 105 and the direct reports of node 105, which are nodes 112, 114, 116, and 118. The workflow begins at step (1) (reference numeral 351) with the system detecting user input on the graphical user interface that is representative of selecting node 114. Node 114 represents an employee and selection of node 114 can be interpreted as an interest to display the direct reports of the employee. Once node 114 has been selected, the workflow reports of node 114. This can be the subnodes that are directly connected to node 114. Once continues by identifying the subnodes (e.g., direct reports) of node 114 at step (2) (reference numeral 352). This can be completed by querying the hierarchical organization for the direct the subnodes have been identified, the workflow can continue by determining a layout to apply to the subnodes at step (3) (reference numeral 353). The layout can be selected from one or more predefined layouts that are applicable to the subnodes. The applicability of a predefined layout to the subnodes can be determined by the number of subnodes that exist. In one embodiment, the workflow can attempt to avoid the presence of an empty element in matrix 320 by selecting a layout that fits the subnodes. For example if there are 15 subnodes, then the layouts which may be applicable are 15×1, 3×5, 5×3, and 1×15. Layouts containing 8×2 or 2×8 may not be preferred since populating 15 subnodes into a 8×2 matrix would result in an empty element in the matrix. Here, the workflow can determine that the layout to apply to the subnodes is a two dimensional matrix since the number of subnodes is equal to or above a predefined threshold (threshold is 15). Of the two dimensional matrixes, a 5×3 and 3×5 may be recommended and one of the two can be selected. In one example, the preferred layout can have more rows than columns (e.g., 5×3) since it would reduce horizontal scrolling in organizational chart 300.

Once the layout has been determined, the workflow can continue by presenting the subnodes in a matrix according to the layout at step (4) (reference numeral 354). Here, the layout for matrix 320 is a 5×3 matrix. The subnodes of node 114 (e.g., subnodes 321-335) are presented in matrix 320 according to the layout. Each subnode can be presented as a tile where attributes of the employee corresponding to the subnode can be displayed in the tile. In some embodiments, the tiles used to present the subnodes in a matrix can be different than the tiles used to present nodes in the organizational chart 300. For example, the tiles used to represent nodes in the organizational chart can be larger in size. As a result, the type font can be larger in size or additional information can be presented in the tiles that represent the nodes. Matrix 320 can disappear from organizational chart 100 when user input representative of selecting node 114 a second time is detected. Selecting a node a first time can cause the subnodes of the selected node to appear in organizational chart 300 while selecting the node a second time can cause the subnodes of the selected node to disappear from organizational chart 300.

FIG. 4 another illustrates a workflow for presenting a second selected node in an organizational chart according to one embodiment. Organizational chart 400 can be presented in response to the selection of node 116 in organizational chart 300 of FIG. 3. As shown here, the second node detected resides in the same horizontal layer as an earlier selected node (node 114). Here, the workflow begins by detecting a second node being selected at step (1) (reference numeral 451). Selection of the second node can be understood as an interest to present the direct reports of the second node in organizational chart 400. Once the second node has been selected, the workflow continues by identifying a second set of subnodes at step (2) (reference numeral 452). The subnodes can represent the direct reports of the employee that corresponds with node 116. Here, subnodes 421-424 represent the direct reports of node 116. After the second set of subnodes are identified, the workflow continues by determining the layout for the second set of subnodes at step (3) (reference numeral 453). The layout for the second set of subnodes can be determined using the same approach as determining the layout for the first set of subnodes (the subnodes of matrix 320). Here, the layout for the second set of subnodes is a vertical vector when the number of subnodes is below a predefined threshold of 15. Alternatively if the number of subnodes is greater than or equal to the predefined threshold of 15, a two dimensional matrix is used as the layout.

Once the layout has been determined, the workflow continues by presenting the second set of subnodes in a matrix according to the layout. Here, the matrix is based on the layout of a vertical vector and as a result, subnodes 421-424 are presented in matrix 420 as a vertical vector. In some embodiments, the workflow can adjust for minimum spacing requirements at step (5) (reference numeral 455). While adjusting for the minimum spacing requirement, the workflow may horizontally shift other nodes (particularly parent nodes of the second set of subnodes) so that the parent nodes of the subnodes appear above the matrix at step (6) (reference numeral 456). In one embodiment, the workflow can check for and adjust the spacing within the organizational chart to ensure that the minimum spacing requirements are satisfied before presenting matrix 420. In another embodiment, the workflow can initially present matrix 420 in organizational chart 400 and then incrementally move the nodes, subnodes, and matrixes in organizational chart 400 until the minimum spacing requirements are satisfied. The movement can be animated. For example, the workflow can present matrix 320 slowly shifting horizontally away from matrix 420 until the minimum spacing requirement is satisfied. While matrix 320 is shifting, node 114 can also shift along with matrix 320. Shifting node 114 can also cause node 112 to shift along with node 114 to ensure that the minimum spacing requirement between node 112 and 114 is not violated.

As described above, the system can adjust the layout of the matrix based on the number of subnodes that are to be presented. In some embodiments, the system can alternatively adjust the layout of the matrix to be presented in the organizational chart based on the space available in the browser window. FIG. 5 illustrates another workflow for presenting a selected node in an organizational chart according to one embodiment. As shown here, organizational chart 500 is presented within browser window 510. Organizational chart 500 includes nodes 105, 112, 114, 116, and 118. These nodes occupy portion 501 of browser window 510, also known as the used space of browser window 510. Browser window 510 also includes portion 502 which is the available space of browser window 510. The available space is the parts of browser window 510 that are available for the presentation of a matrix. The system can dynamically adjust the layout of a matrix based on the available space. In some examples, the available space can specify an area of browser window 510, as measured in pixels.

Here, the workflow can begin by detecting user input representative of selecting node 114 of organizational chart 500 at step (1) (reference numeral 551). The workflow can then continue by identifying the subnodes of the selected node at step (2) (reference numeral 552). The subnodes can be identified by querying a hierarchical organization for the direct reports of the employee being represented by node 114. Once the subnodes have been identified, the workflow can continue by determining the available space in browser window 510 at step (3) (reference numeral 553). The available space is the portion of the usable space in browser window 510 that is available to the system to add to organizational chart 500. In some examples where browser window 510 allows for scrolling, the usable space within browser window 510 can extend past the viewable space of browser 510. For instance, the usable space in browser window 510 can be 120% of the viewable space in browser window if browser window 510 is configured to allow for 20% scrolling.

The available space in browser window 510 can be calculated using various methods. In one embodiment, the system can determine the available space by identifying the portion of the usable space in browser window 510 that resides below the selected node (node 114). Here, browser window 510 does not allow for scrolling so portion 502 represents the area of browser window 510 that resides below selected node 114. If subnodes or matrixes of organizational chart 500 already exist in portion 502, then the available space would be the part of portion 502 that is currently not being utilized by organizational chart 500. In another embodiment, the system can determine the available space by first calculating the used space within browser window 510. Calculation of the used space can be performed by measuring the portion of browser window 510 that is currently be utilized to present organizational chart 500 when node 114 is selected. Here, portion 501 has been measured as the part of browser window 510 that is being utilized to present organizational chart 500 when the selection of node 114 is detected. The system can subtract portion 501 from the usable space of browser window 510 to determine the available space. As shown here, the available space is portion 502. In some examples, the available space and the used space can take into consideration in screen resolution. Thus, calculation of the used space and the available space can be measured in pixels. By knowing how the dimensions of the available space in pixels, the system can determine the number and orientation of tiles that can fit within the available space. This is by knowing the default size of each tile that is used to represent a subnode.

Once the available space has been determined, the workflow continues by determining the potential layout for the subnodes at step (4) (reference numeral 554). The potential layout can depend on the number of subnodes to present. For example, the system can determine that there are multiple layouts to present the nine subnodes. The potential layouts can include a 2×5 matrix, a 5×2 matrix, and a 3×3 matrix. In one embodiment, the system may provide potential layouts which minimize the occurrence of empty elements in the layout. Here, the 2×5 matrix can store 10 elements. Given that there are only nine subnodes, one element in the matrix will remain empty. Similarly, the 5×2 matrix will have one empty element. The 3×3 element will have zero empty elements. A 4×3 matrix can be determined to not be a potential layout since the layout would result in two empty elements. In some examples, a variable on the system can be configured to specify the maximum number of empty elements in the layout.

At step (5) (reference numeral 555), the workflow can select a layout from the potential layouts according to the available space. In one embodiment, a potential layout without empty elements can be preferred. Here, the system may determine that while a 3×3 layout is preferred when there are nine subnodes, three rows cannot fit within the available space. This determination can be made based on the dimensions of a tile used to represent a subnode and the dimensions of the available space. As a result, other layouts are considered. The system can determine that the available space allows for at most a matrix containing two rows. As a result, the system can select a 2×5 layout based on the available space in browser window 510 over a 5×2 layout or a 3×3 layout. Once the layout has been selected, the workflow continues by presenting the subnodes in matrix 520 according to the selected layout at step (6) (reference numeral 556). As shown here, subnodes 521-529 are being presented in matrix 520 in a multi-dimensional matrix where the layout of the matrix is determined based on the available space.

In some instances, user input can be received to resize the browser window. Resizing the browser window can alter the dimensions of the browser window. As a result, the organizational chart which use to fit within the useable space of the browser window may no longer fit. In these scenarios, the system may adjust the organizational chart to fit within the browser window. FIG. 6 illustrates a workflow for altering an organizational chart in response to a window resize according to one embodiment. Organizational chart 600 includes node 105, 112, 114, 116, and 118. In its initial state, organizational chart 600 can appear similar or substantially similar to organizational chart 500 of FIG. 5. Node 114 can be connected to matrix 520 which contains subnodes. Organizational chart 500 can transition to organizational chart 600 in response to a resize of the browser window from browser window 510 to browser window 610.

At step (1) (reference numeral 651), the workflow can detect user input representative of resizing browser window 610. In one example, the user input can be a click and drag gesture performed by a mouse or other peripheral device. In another example, the user input can be a touch gesture performed on a touch screen display. Once the window resize has been detected, the workflow can continue by determining that a matrix (or other element) of organizational chart 500 overlaps the boundary of usable area of resized browser window 610 at step (2) (reference numeral 652). During resizing, the usable area of browser window 610 can change dimensions. As a result, elements of organizational chart 500 which previously resided within the usable area of browser window 610 now reside wholly or partially outside the usable area of browser window 610. These elements of organizational chart 500 are known as overlapping elements of organizational chart 500. In this example, matrix 520 is an overlapping element since it is partially outside the usable area of browser window 610.

At step (3) (reference numeral 653), the workflow determines the potential layouts that are available for the overlapping matrix. For example, matrix 520 is a 2×5 matrix but other potential matrixes are a 5×2 matrix and a 3×3 matrix. Once the other potentially matrixes have been identified, the workflow continues by select a layout according to the available space in resized browser window 610 at step (4) reference numeral. Here, the available space is portion 602 of browser window 610. Out of the potential layouts (e.g., 2×5, 5×2, and 3×3), the system determines that layout 3×3 would allow the overlapping matrix to fit within the available area of resized browser window 610. As a result, the workflow presents the subnodes of matrix 520 in a 3×3 table, thus resulting in matrix 620. As shown here, matrix 620 now fits within the available space of browser window 610. In some examples, modifying a matrix may cause the modified matrix to collide with other elements in organizational chart 600. As a result, organizational chart 600 can iteratively be modified until all elements of organizational chart 600 fit within browser window 610.

In some instances, the available space within browser window 510 may be insufficient to present any of the potential layouts of matrix 620. This can be due to the fact that there are too many subnodes to present in the available space. Alternatively, this can be due to the fact that the resized browser window is leaves not enough available space to present matrix 620. In one embodiment, the system can recognize this condition and automatically close matrix 620, thus making it appear as though node 144 has not been selected. In another embodiment, the system can recognize this condition and automatically scale organizational chart 600 such that organizational chart 600 fits within browser window 610. Resizing organizational chart 600 can cause the tiles of organizational chart 600 to shrink in size and thus occupy fewer pixels. The smaller sized tiles can present fewer attributes than the larger tiles.

FIGS. 7a, 7b, and 7c illustrate exemplary tile templates according to one embodiment. Each tile template is associated with a different sized tile which can be used to represent a node or subnode in the organizational chart. The system may select a tile template based on the scale of the organizational chart. Tile templates for larger tiles can present more information than tile templates for smaller tiles. As described above, the system may scale down the organizational chart so that it fits within the useable area of the browser window.

FIG. 7a illustrates a large tile template according to one embodiment. Tile template 700 a is configured to present various attributes of the node (or subnode). Tile template 700 a includes a profile picture associated with the node, the name of the employee associated with the node, the title of the employee associated with the node, the number of employees who directly report to the employee associated with the node, and/or additional information on the employee associated with the node. More or fewer attributes can be presented in tile template 700 a. In one embodiment, the additional information presented can be role based. Thus, the information being presented in tile template 700 a can depend on the party generating the organizational chart. For example if the organizational chart is being generated for a manager, the additional information for each node can include the salaries of the employees who directly report to the manager. In contrast if the organizational chart is being generated for a low level employee, the salaries of the employee's colleagues may not be presented as additional information. In another embodiment, the additional information presented can be context based. In other words, the additional information presented can depend on the node (or subnode) which the tile represents. For example, the system may not present an attribute on the number of direct reports for a tile that represents a low level employee without direct reports. As another example, the system may not present an attribute on the amount of time off which the employee has accrued if the employee being represented by the tile is not a full time employee. Thus, one or more attributes of the node (or subnode) can affect the context of the tile and thus affect what attributes will be presented in the tile. In some embodiments, one or more of the attributes presented can be selectable. Selecting the attribute can be interested by the system as input representative of a request to present the direct reports of the tile in the organizational chart. For example, the number of direct reports attribute can be selectable (i.e., actionable) where selecting the number of direct reports attribute is processed by the system as a request to present the direct reports of the tile in the organizational chart. To remove the direct reports from the organizational chart, the attribute can be selected a second time. For example selecting the number of direct reports attribute can cause the direct reports to be removed from the organizational chart.

FIG. 7b illustrates a medium tile template according to one embodiment. When the organizational chart is scaled down past a predefined threshold, the system may utilize tile template 700 b instead of tile template 700 a when presenting the organizational chart. By using a smaller tile template, the overall size of the organizational chart will be smaller. As shown here, tile template 700 b includes a profile picture, a name, a title, and a number of direct reports. As described above, one or more of the attributes presented can be actionable where selecting the attribute can result in an expansion of the organizational chart to display the direct reports of the employee being represented by the tile.

FIG. 7c illustrates a small tile template according to one embodiment. As shown here, tile template 700 c includes even fewer attributes than template 700 b and thus is even smaller in size. When the scaling factor of the organizational chart falls below another threshold, then tile template 700 c can be utilized in generating the organizational chart. In some embodiments, the minimum tile template size that can be applied to an organizational chart can depend on the screen resolution and the size of the screen on the client device that is presenting the organizational chart. For example, it may be undesirable to apply the small tile template on a small screen with high resolution since the actual size of the tiles may be too small for a user to read. The system can implement a conditional check which determines the actual pixel size based on the screen resolution and the size of the screen. The pixel size can then be combined with the size of the tile to calculate the actual size of the tile. If the actual size of the tile is smaller than a predefined threshold, then the system may determine that the tile template is too small for presentation on the client's device and automatically move up to a larger tile template that satisfies the predefined threshold.

FIGS. 8a, 8b, and 8c illustrate exemplary tile templates according to one embodiment. These tile templates can be applied to present tiles in matrixes of the organizational chart. As shown, tile templates for tiles in a matrix can be smaller than the tile templates for tiles not part of a matrix (e.g., tile templates 700 a, 700 b, and 700 c). FIG. 8a illustrates a large tile template according to one embodiment. Tile template 800 a includes a profile picture, name, title, number of direct reports, and additional information. FIG. 8b illustrates a medium tile template according to one embodiment. Tile template 800 b includes a name, title, and number of direct reports. FIG. 8c illustrates a small tile template according to one embodiment. Tile template 800 c includes a name and title. As described above, one or more of these attributes can be actionable. Furthermore, the attributes presented in a given tile template can be context-based or role-based. In some embodiments, the system dynamically adjust the layout of the organizational chart when the organizational chart does not fit within the browser window by using a two-step process. In the first step, the system can adjust the layout and spacing of different tiles in the organizational chart to try and fit the organizational chart within the usable area of a browser window. If adjusting the layout and spacing does not resolve the issue, the system can further adjust the scaling of the organizational chart. The system can go repeat these steps until the organizational chart fits within the browser window.

Exporting Organizational Charts

In some examples, it can be desirable to export the organizational chart (or a portion of the organizational chart) that is being displayed. For example, an exported portion of the organizational chart can be useful to include in a company report or other document or presentation which the employee is working on. In some embodiments, the system can present an export canvas that is configured to identify a portion of the organizational chart to export. The portion to export can be the part of the organizational chart that lies within the boundaries of the export canvas. Through use of the export canvas, the user can visually preview the portion of the organizational chart to be exported. In some examples, the user can move and resize the export canvas until the desired portion of the organizational chart is within the boundaries of the export canvas. Once the desired portion is within the boundaries of the export canvas, an instruction can be provided to export the desired portion. The system can process the instruction and export the desired portion of the organizational chart. Depending on the settings of the export, the desired portion can be exported as an image, a pdf, a live link (which the user can interact with) or other export format.

FIG. 9 illustrates a browser window containing an export menu according to one embodiment. Browser window 900 includes export menu 1000 and organizational chart 950. Organizational chart 950 can be occupy the portion of browser window 900 that is not being occupied by export menu 1000. Therefore, the area of browser window 900 besides the area occupied by export menu 1000 can be used to present organizational chart 950. Export menu 1000 can be positioned at a predefined location in browser window and be fixed dimensions. Here, export menu 1000 is positioned along the top boarder of browser window 900 and is configured to occupy a fixed space of browser window 900. In some examples, export menu 1000 can retract and disappear from browser window 900 when not in use. For instance, export menu 1000 can appear as shown in FIG. 9 when a gesture is detected near the top border of browser window 900 and disappear into the top border of browser window 900 when a gesture is detected a distance away from the top border of browser window 900.

Browser window 900 can further include export canvas 960. Export canvas 960 can be configured to identify a portion of organizational chart 950 to be exported. In some embodiments, the portion of organizational chart 950 which lies within the boundaries of export canvas 960 can be the portion that is to be exported. In one embodiment, organizational chart 950 can be presented on a first layer of browser window 900 while export canvas 960 is presented on a second layer of browser window 900. The second window can be translucent and overlay the first layer. This allows export canvas 960 to be moved around browser window 900 without interfering with the underlying organizational chart 960 which is being presented on the first layer. In other embodiments, organizational chart 950 and export canvas 960 can be presented on a single layer where export canvas 960 is rectangular box that is transparent in nature so that nodes of the underlying organizational chart 950 can be seen.

FIG. 10 illustrates an export menu according to one embodiment. Export menu 1000 includes a plurality of fields that allow a user to configure the parameters of the export file. The export file can contain a portion of the organizational chart that is within the export canvas. Export menu 1000 can include export format field 1010 which is configured to specify the export format of the export file. The export format can be a live link (e.g., a web link) that allows the recipient to view the portion of the organizational chart on a web browser. When the live link is selected, an instruction can be transmitted to the system to present a web-based version of the portion of the organizational chart. The recipient can then interact with the web-based version to explore the portion of the organizational chart by opening and closing nodes. In other examples, the export format can also be a PowerPoint presentation, a pdf file, or an image.

Export menu 1000 can further include image quality field 1020. Image quality field 1020 can specify the image quality of the export file. For example, the image quality can be set to normal, fine, or superfine, similar to the image quality setting on a digital camera. Export menu 1000 can further include width field 1030 and height field 1040. Width field 1030 and height field 1040 can specify the dimensions of the export canvas. In one embodiment, the system can automatically resize the export canvas in response to adjustments made to width field 1030 or height field 1040. Similarly, the system can automatically adjust width field 1030 or height field 1040 in response to touch gestures used to resize the export canvas. In other words, the width and height of the export canvas can be directly related to the values stored in width field 1030 and height field 1040.

Export menu 1000 can further include multiple pages flag field 1050 and page selector field 1060. Multiple pages flag field 1050 can be set when it is desirable to export the organizational chart (or a portion of the organizational chart) across multiple pages. If multiple pages flag 1050 is set, then width field 1030 and height field 1040 can be independent of the dimensions of the export canvas. This is because width field 1030 and height field 1040 specify the dimensions of a page for export. If the export is occurring across multiple pages, then the dimensions of the export canvas can be multiple pages. In one embodiment, the system can apply a visual indicator to the page identified by page selector field 1060. The page selected via page selector 1060 can appear highlighted or otherwise visually modified so that it can be easily identifiable.

Export menu 1000 can further include autofit flag 1070. Autofit flag 1070 can be configured to automatically export the organizational chart. In one embodiment, the automatic export can be configured to automatically partition the organizational chart into multiple sections that can fit within each page. The size of each page can be specified via weight field 1030 and height field 1040. Once the user has selected the desired export parameters and optionally positioned the export canvas to the desired location in the organizational chart, one flag 1080 can be selected. The system can begin generating the export file when done flag 1080 is selected.

FIG. 11 illustrates a browser window according to one embodiment. Browser window 1100 includes export menu 1000, organizational chart 1110, and export canvas 1120. Organizational chart 1110 includes tiles 1151-1164, which represent a portion of the organization where parent nodes represent managers and children nodes represent the subordinates of the managers. For example, node 1153 can represent a manager who manages the subordinates being represented by tiles 1156-1164. In some embodiments, organizational chart 1110 can be presented on a first layer of browser window 1100.

Export canvas 1120 can be presented on a second layer of browser window 1100 that overlays the first layer. As shown, the position of export canvas 1120 currently collides with tile 1152 and tile 1155. The system can be configured to detect the existence of a collision and take the proper precautionary steps to prevent the collision. In one embodiment, the system can shift export canvas 1120 in a direction which can prevent the collision. For example, export canvas 1120 can be shifted to the left such that tile 1152 no longer collides with the boundary of export canvas 1120. In another embodiment, the system can resize export canvas 1120 to prevent the collision. For example, export canvas 1120 can be extended to the left to avoid the collision with tile 1152.

In one embodiment, the system can shift or resize export canvas 1120 in a manner which minimizes the adjustments being made. For example, the system can first determine whether the majority of the colliding tile is inside or outside export canvas 1120. If the majority of the colliding tile is within export canvas 1120, then the system can extend or shift export canvas 1120 such that the colliding tile is within the boundaries of export canvas 1120. Alternatively if the majority of the colliding tile is outside export canvas 1120, then the system can extend or shift export canvas 1120 such that the colliding tile is outside the boundaries of export canvas 1120. Here, the majority of tile 1152 is within the boundaries of export canvas 1120. As such, the system can make this determination and either shift or resize export canvas 1120 such that tile 1152 is within the boundaries of export canvas 1120. In one embodiment, the system can make a determination whether to shift or resize export canvas 1120 based on the export menu parameters that have been selected. For example if the multiple pages flag 1050 is selected, then the system can attempt to shift rather than resize since the pages should be the same dimensions. Similarly if multiple pages is not selected, then the system can attempt to resize rather than shift. Alternatively, the system can first attempt to shift, then attempt to resize. For example, the system can attempt to shift to prevent the collisions with a tile. However, shifting export canvas 1120 can cause other tiles to collide with other boundaries of export canvas 1120. As a result, the system can resize export canvas 1120 when shifting fails. Here, shifting export canvas 1120 slightly to the left can avoid the collision with tiles 1152 and 1155. As a result, the system can shift export canvas 1120 slightly to the left rather than resizing export canvas 1120. In some examples, the shifting and resizing of export canvas 1120 can occur dynamically when a collision is detected between export canvas 1120 and the tiles of organizational chart 1110. In other examples, the shifting and resizing of export canvas 1120 can occur as part of the export process.

In some embodiments, the system can automatically fit the organizational chart across multiple pages. To do so, the system can automatically determine the location of one or more page breaks based on the dimensions of the export canvas as specified in the export menu. FIG. 12 illustrates a browser window according to another embodiment. Browser window 1200 includes export menu 1000 and organizational chart 1210. Organizational chart 1210 includes tiles 1251-1265. Here, the parameters in export menu 1000 specify that organizational chart 1210 is to be automatically fit within export canvas 1220. In some examples, the dimensions of export canvas 1220 can be defined in export menu 1000. Based on the dimensions of export canvas 1220 and the space occupied by organizational chart 1210, the system can automatically determine the location to place page break 1290 to separate organizational chart 1210 into two pages. In other examples, the system can generate multiple page breaks to separate or partition organizational chart 1210. After the page breaks are placed within organizational chart 1210, the system can position the export canvases on top of the separate pages to fit the tiles of organizational chart 1210 within each export canvas. In one embodiment, the export canvases can be visible so that a user can confirm the location of the page breaks and the position and size of the export canvases. Once committed, the system can generate multiple export pages to store organizational chart 1210.

FIG. 13a illustrates a first export page according to one embodiment. As shown, export page 1300 a can be based on export canvas 1220 a of FIG. 12. Export page 1300 a includes tiles 1251-1255. In some embodiments, the system can also add in connection points to assist in reestablishing connections for tiles on different export pages. As shown here, export page 1300 a includes connection points 1310 and 1320. Each connection point can have be identified using a visual indicator such as a letter, color, or shape, for example. FIG. 13b illustrates a second export page according to one embodiment. As shown, export page 1300 b can be based on export canvas 1220 b of FIG. 12. Export page 1300 b includes tiles 1256-1265. Export canvas 1300 b further includes connection points 1310 and 1320. Connection point 1310 is a visual indicator to assist in reestablishing the connection between tile 1253 of export page 1300 a and tile 1256 of export page 1300 b. Similarly, connection point 1320 is a visual indicator to assist in reestablishing the connection between tile 1353 of export page 1300 a and tile 1257 of export page 1300 b.

In some embodiments, export menu 1000 can also include parameters to cause the system to automatically export multiple levels of an organization. For example, the system can automatically export a first export page that contains a top level view of the organization. The top level view can include the upper level managers and lower level managers. The system can then automatically export multiple export pages that each contain a team view for a lower level manager. For example, the system can export the team members for a lower level manager in a second export page. All of the export pages (which include the top level view and the team views) can be packaged together in a single export file.

FIG. 14 illustrates a process for updating an export canvas according to one embodiment. Process 1400 can be stored in computer readable code and executed by a processor. For example, process 1400 can be part of the computer readable code that is executed by computer system 1510 of FIG. 15. Process 1400 can begin by presenting an organizational chart within a first layer of a window at 1410. The organizational chart can include a plurality of nodes that each represent an employee within an organization. Each node can be represented as a tile within the first layer of the window. The lines connecting the tiles can represent the relationships between employees of the organization. Process 1400 can continue by presenting an export canvas within a second layer of the window that overlays the first layer at 1420. The export canvas can be configured to identify a portion of the organizational chart for export that lies within the boundaries of the export canvas. Process 1400 can then continue by detecting an adjustment to the export canvas at 1430. In one example, the adjustment can be a resize of the export canvas. In another example, the adjustment can be a repositioning of the export canvas.

Process 1400 can continue by determining that the adjustment causes a boundary of the export canvas to collide with a tile representing a node of the organizational chart at 1440. The system can make this determination by checking the boundaries of the export canvas for a collision with a tile of the organizational chart. If a collision has occurred, process 1400 can continue by automatically updating the export canvas to prevent the collision at 1450. In one embodiment, updating the export canvas can include repositioning the export canvas in a manner such that the collision no longer occurs. In other words, the export canvas remains the same dimensions but is repositioned to avoid the collision. In another embodiment, updating the export canvas can include resizing the export canvas in a manner such that the collision no longer occurs. In some embodiments, the system can first attempt to reposition the export canvas. If repositioning the export canvas is unsuccessful in preventing the collision (e.g., repositioning the export canvas causes another tile to collide with the boundaries of the export canvas), then the system can then resize the export canvas. In yet other embodiments, the system can both resize the tiles within the organizational chart to optimize the manner in which the tiles fit within the export canvas. For example, the system can reduce the size of the tiles within the organizational chart to improve the fitment of the tiles within the export canvas. Resizing the tiles can involve updating the tiles so that they are based on a different tile template.

An exemplary computer system 1500 is illustrated in FIG. 15. Computer system 1510 includes a bus 1505 or other communication mechanism for communicating information, and a processor 1501 coupled with bus 1505 for processing information. Computer system 1510 also includes memory 1502 coupled to bus 1505 for storing information and instructions to be executed by processor 1501, including information and instructions for performing the techniques described above, for example. This memory may also be used for storing variables or other intermediate information during execution of instructions to be executed by processor 1501. Possible implementations of this memory may be, but are not limited to, random access memory (RAM), read only memory (ROM), or both. A storage device 1503 is also provided for storing information and instructions. Common forms of storage devices include, for example, a hard drive, a magnetic disk, an optical disk, a CD-ROM, a DVD, a flash memory, a USB memory card, or any other medium from which a computer can read. Storage device 1503 may include source code, binary code, or software files for performing the techniques above, for example. Storage device and memory are both examples of computer readable mediums.

Computer system 1510 may be coupled via bus 1505 to a display 1512, such as a cathode ray tube (CRT) or liquid crystal display (LCD), for displaying information to a computer user. An input device 1511 such as a keyboard and/or mouse is coupled to bus 1505 for communicating information and command selections from the user to processor 1501. The combination of these components allows the user to communicate with the system. In some systems, bus 1505 may be divided into multiple specialized buses.

Computer system 1510 also includes a network interface 1504 coupled with bus 1505. Network interface 1504 may provide two-way data communication between computer system 1510 and the local network 1520. The network interface 1504 may be a digital subscriber line (DSL) or a modem to provide data communication connection over a telephone line, for example. Another example of the network interface is a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links are another example. In any such implementation, network interface 1504 sends and receives electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information.

Computer system 1510 can send and receive information, including messages or other interface actions, through the network interface 1504 across a local network 1520, an Intranet, or the Internet 1530. For a local network, computer system 1510 may communicate with a plurality of other computer machines, such as server 1515. Accordingly, computer system 1510 and server computer systems represented by server 1515 may form a cloud computing network, which may be programmed with processes described herein. In the Internet example, software components or services may reside on multiple different computer systems 1510 or servers 1531-1535 across the network. The processes described above may be implemented on one or more servers, for example. A server 1531 may transmit actions or messages from one component, through Internet 1530, local network 1520, and network interface 1504 to a component on computer system 1510. The software components and processes described above may be implemented on any computer system and send and/or receive information across a network, for example.

The above description illustrates various embodiments of the present invention along with examples of how aspects of the present invention may be implemented. The above examples and embodiments should not be deemed to be the only embodiments, and are presented to illustrate the flexibility and advantages of the present invention as defined by the following claims. Based on the above disclosure and the following claims, other arrangements, embodiments, implementations and equivalents will be evident to those skilled in the art and may be employed without departing from the spirit and scope of the invention as defined by the claims. 

What is claimed is:
 1. A computer-implemented method, comprising: presenting, by a processor, an organizational chart within a first layer of a window, the organizational chart including a plurality of nodes that each represent an employee within an organization, wherein each node is represented as a tile within the first layer of the window; presenting, by the processor, an export canvas within a second layer of the window that overlays the first layer, wherein the export canvas is configured to identify a portion of the organizational chart for export that lies within the within the boundaries of the export canvas; detecting, by the processor, an adjustment to the export canvas; determining, by the processor, that the adjustment causes a boundary of the export canvas to collide with a tile representing a node of the organizational chart; and automatically updating, by the processor, the export canvas to prevent the collision.
 2. The computer-implemented method of claim 1, further comprising: presenting, by the processor, an export menu within the window, the export menu being configured to provide a plurality of options for exporting the organizational chart; and automatically updating, by the processor, an option from the plurality of options that is associated with the dimension when the dimension is updated to prevent the collision.
 3. The computer-implemented method of claim 1, wherein the second layer is a transparent layer that overlays the first layer.
 4. The computer-implemented method of claim 1, wherein automatically updating the export canvas chart comprises: determining, by the processor, that a majority of the tile is within the export canvas; and increasing, by the processor, a dimension of the export canvas such that the tile is within the boundary of the export canvas.
 5. The computer-implemented method of claim 1, wherein automatically updating the export canvas chart comprises: determining, by the processor, that a majority of the tile is within the export canvas; and shifting, by the processor, the export canvas such that the tile is within the boundary of the export canvas.
 6. The computer-implemented method of claim 1, wherein automatically updating the dimension of the export canvas chart comprises: determining, by the processor, that a majority of the tile is outside the export canvas; and reducing, by the processor, a dimension of the export canvas such that the tile is outside the boundary of the export canvas.
 7. The computer-implemented method of claim 1, wherein automatically updating the dimension of the export canvas chart comprises: determining, by the processor, that a majority of the tile is outside the export canvas; and shifting, by the processor, the export canvas such that the tile is outside the boundary of the export canvas.
 8. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions for: presenting an organizational chart within a first layer of a window, the organizational chart including a plurality of nodes that each represent an employee within an organization, wherein each node is represented as a tile within the first layer of the window; presenting an export canvas within a second layer of the window that overlays the first layer, wherein the export canvas is configured to identify a portion of the organizational chart for export that lies within the within the boundaries of the export canvas; detecting an adjustment to the export canvas; determining that the adjustment causes a boundary of the export canvas to collide with a tile representing a node of the organizational chart; and automatically updating the export canvas to prevent the collision.
 9. The non-transitory computer readable storage medium of claim 8, further comprising: presenting an export menu within the window, the export menu being configured to provide a plurality of options for exporting the organizational chart; and automatically updating an option from the plurality of options that is associated with the dimension when the dimension is updated to prevent the collision.
 10. The non-transitory computer readable storage medium of claim 8, wherein the second layer is a transparent layer that overlays the first layer.
 11. The non-transitory computer readable storage medium of claim 8, wherein automatically updating the export canvas chart comprises: determining that a majority of the tile is within the export canvas; and increasing a dimension of the export canvas such that the tile is within the boundary of the export canvas.
 12. The non-transitory computer readable storage medium of claim 8, wherein automatically updating the export canvas chart comprises: determining that a majority of the tile is within the export canvas; and shifting the export canvas such that the tile is within the boundary of the export canvas.
 13. The non-transitory computer readable storage medium of claim 8, wherein automatically updating the dimension of the export canvas chart comprises: determining that a majority of the tile is outside the export canvas; and reducing a dimension of the export canvas such that the tile is outside the boundary of the export canvas.
 14. The non-transitory computer readable storage medium of claim 8, wherein automatically updating the dimension of the export canvas chart comprises: determining that a majority of the tile is outside the export canvas; and shifting the export canvas such that the tile is outside the boundary of the export canvas.
 15. A computer implemented system, comprising: one or more computer processors; and a non-transitory computer-readable storage medium comprising instructions, that when executed, control the one or more computer processors to be configured for: presenting an organizational chart within a first layer of a window, the organizational chart including a plurality of nodes that each represent an employee within an organization, wherein each node is represented as a tile within the first layer of the window; presenting an export canvas within a second layer of the window that overlays the first layer, wherein the export canvas is configured to identify a portion of the organizational chart for export that lies within the within the boundaries of the export canvas; detecting an adjustment to the export canvas; determining that the adjustment causes a boundary of the export canvas to collide with a tile representing a node of the organizational chart; and automatically updating the export canvas to prevent the collision.
 16. The computer implemented system of claim 15, further comprising: presenting an export menu within the window, the export menu being configured to provide a plurality of options for exporting the organizational chart; and automatically updating an option from the plurality of options that is associated with the dimension when the dimension is updated to prevent the collision.
 17. The computer implemented system of claim 15, wherein the second layer is a transparent layer that overlays the first layer.
 18. The computer implemented system of claim 15, wherein automatically updating the export canvas chart comprises: determining that a majority of the tile is within the export canvas; and adjusting a dimension of the export canvas such that the tile is within the boundary of the export canvas.
 19. The computer implemented system of claim 15, wherein automatically updating the export canvas chart comprises: determining that a majority of the tile is within the export canvas; and shifting the export canvas such that the tile is within the boundary of the export canvas.
 20. The computer implemented system of claim 15, wherein automatically updating the dimension of the export canvas chart comprises: determining that a majority of the tile is outside the export canvas; and shifting the export canvas such that the tile is outside the boundary of the export canvas. 